Data conversion system

ABSTRACT

Systems for converting data are provided. In one embodiment, a data conversion system is provided that includes a client module. The client module includes a conversion portion and an existing file segment database. The conversion portion is configured to partition a file to be converted into a plurality of file segments. The existing file segment database portion is configured to store one or more existing file segments and one or more key values, each of the one or more key values associated with one of the one or more existing file segments. The conversion portion is also configured to assign a key value to each of the plurality of file segments and to create a key value file with the assigned key values.

FIELD

Embodiments of this disclosure relate generally to data conversion. Morespecifically, the embodiments relate to a system for data conversion.

BACKGROUND

Many of today's markets like financial, legal, military, education,entertainment and medical are all seeing their data grow exponentially.The market has coined the term “big data” to explain the rise of largedatabases and the growing amount of data being driven by every industry.The growing trend to maintain large amounts of structured andunstructured data is largely led by growing Governmental regulations andcompliances. These factors are leading to the explosive growth of thecloud and data storage technologies. Also, with the prevalence of bigdata, it becomes increasingly important to compress the data to allowfor more efficient storage and quicker transmission of the data overboth public and private networks.

SUMMARY

Systems for converting data are described that can be used in a numberof applications including, but not limited to, secure transmission ofdata from one location to another, secure data backup, and general datastorage.

In particular, the embodiments described herein provide data conversionby: identifying patterns in a data file, assigning a code or key valueto each of these patterns, building a library of codes or key values ofwhich each code or key value is associated with a unique pattern,replacing the data file with a key value file made up of the codes orkey values, and compressing and/or encrypting the key value file.

In one embodiment, a data conversion method is provided. The dataconversion method includes partitioning the data file into a pluralityof file segments. The data conversion method also includes assigning aplurality of key values for each of the plurality of file segments.Also, the data conversion method includes forming a key value file fromthe plurality of key values.

In another embodiment, a data conversion system is provided. The dataconversion system includes a client module. The client module includes aconversion portion and an existing file segment database. The conversionportion is configured to partition a file to be converted into aplurality of file segments. The existing file segment database portionis configured to store one or more existing file segments and one ormore key values, each of the one or more key values associated with oneof the one or more existing file segments. The conversion portion isalso configured to assign a key value to each of the plurality of filesegments and to create a key value file with the assigned key values.

In yet another embodiment, a data conversion device is provided. Thedata conversion device includes a conversion portion and an existingfile segment database portion. The conversion portion is configured topartition a file to be converted into a plurality of file segments. Theexisting file segment database portion is connected to the conversionportion. Also, the existing file segment database portion is configuredto store one or more existing file segments and one or more key values,each of the one or more key values associated with one of the one ormore existing file segments. The conversion portion is also configuredto assign a key value to each of the plurality of file segments and tocreate a key value file with the assigned key values.

DRAWINGS

FIG. 1 is a flow chart of a data conversion method described herein.

FIG. 2 schematically depicts a data conversion system described herein.

FIG. 3 schematically depicts an architecture of a computing device andcomputing system optionally used in connection with computer-implementedmethods described in this document.

DETAILED DESCRIPTION

The following description describes systems for converting data. Thedescribed systems can be used in a number of applications including, butnot limited to, secure transmission of data from one location to anotherand secure data backup.

In particular, the embodiments described herein provide data conversionby: identifying patterns in a data file, assigning a code or key valueto each of these patterns, building a library of codes or key values ofwhich each is associated with a unique pattern, replacing the data filewith a key value file made up of the codes or key values, andcompressing and/or encrypting the key value file. The embodimentsdescribed herein allow the size of a file to be reduced significantly.This can lead to an increased data transmission rate and an increasedstorage capability, as the converted data files being transmitted orstored are significantly smaller than the data files they replace.

With reference to FIG. 1, a data conversion method 100 that can beimplemented by one or more computer devices is illustrated. In someembodiments, the data conversion method 100 can be performed by a singlecomputer device. In other embodiments, portions of the data conversionmethod 100 can be distributed amongst a plurality of computer devices(as described below with respect to FIG. 2).

At 105 a file to be converted is converted into a raw file. As discussedherein, a raw file is a file of raw data that is a lower level of datathan the data stored in the file to be converted. In some embodiments,the lower level of data can be a cross global data format such as, forexample, a binary code format. In other embodiments, the lower level ofdata can be a data format that may not be a cross global format such as,for example, an American Standard Code for Information Interchange(ASCII) data format.

In some embodiments, when a file is to be converted, the file(regardless of the file format type) can be converted into, for example,a binary code file. For example, in some embodiments, the data in thefile to be converted can be converted into a data file with binary codedata.

In some embodiments, the raw file can be compressed using, for example,an industry standard compression process prior to the data conversionmethod 100 proceeding to 110.

At 110, the data in the raw file is partitioned into a plurality of rawfile segments. In some embodiments, when the raw file is a binary codefile, the plurality of raw file segments can be binary strings. The rawfile can be partitioned based on a variable size delimiter and/or afixed size delimiter. A variable size delimiter can be, for example, atevery space or gap in the raw file or a data pattern in the raw file isrecognized (e.g., when a string of data matches en existing raw filesegment stored in a reference library or a reference library database).A fixed size delimiter can be, for example, after every X number ofbytes (where X can be a predetermined number set, e.g., by the user, thecomputer device, etc.). In yet some other embodiments, the embodimentslisted above can be combined such that the raw file can be partitioned,for example, at every space or gap in the raw file, or after every Xnumber of bytes when a space or gap is not found in the X number ofbytes.

When the raw file is a binary code file, the binary code file can besegmented into binary strings based on a variable size delimiter (e.g.,a recognized binary string pattern) or based on a fixed length delimiter(e.g., a fixed length string into a base-64 compliant binary string).

At 115, a raw file segment is compared to existing raw file segment(s)stored in a reference library of a raw file segment database to see ifthe raw file segment matches an existing raw file segment. In someembodiments, the raw file segments can be stored in a shared modeldatabase. In other embodiments, the raw file segment database may storemultiple reference libraries with each reference library provided for aparticular file type. For example, the raw file segment database mayinclude a text file reference library, a video file reference library,an application file reference library, etc.

If a match is found at 120, the data conversion method 100 proceeds to125. At 125, the raw file segment is replaced with a key valuecorresponding to the existing raw file segment and stored in the rawfile segment database. A key value, as discussed herein, refers to acode or value having a size less than or equal to the size of theexisting raw file segment. For example, in some embodiments, the keyvalue can be a numerical value such as, for example, a hexadecimalvalue. In other embodiments, the key value can be a non-numerical valuesuch as, for example, an ASCII value. The key value is stored as part ofa key value file. The data conversion method 100 then proceeds to 135.

If a match is not found at 120, the data conversion method 100 proceedsto 130. At 130, the raw file segment is stored in the raw file segmentdatabase and a new key value is assigned to the raw file segment. Insome embodiments, the key value associated with an existing raw filesegment can be changed based on, for example, the frequency that anexisting raw file segment is used. For example, if an existing raw filesegment is determined to be frequently used, the key value stored in theraw file segment database can be changed to a smaller size key value.The data conversion method 100 then proceeds to 125.

At 135, the data conversion method 100 determines whether a key valuehas been assigned to each of the raw file segments partitioned from theraw file. If so, the data conversion method 100 proceeds to 140. If not,the data conversion method 100 proceeds back to 115 where another rawfile segment partitioned from the raw file is compared to the raw filesegment database to see if this raw file segment matches an existing rawfile segment stored in the reference library of the raw file segmentdatabase.

At 140, each of the raw file segments from the raw file is replaced withtheir corresponding key values and the corresponding key values arecombined to create a key value file. While the key value file in thisembodiment is created after a key value is assigned to each of the rawfile segments, it is appreciated that in other embodiments the key valuefile can be updated while a key value is assigned to each of the rawfile segments.

At 145, the key value file undergoes a compression process to create acompressed key value file. In some embodiments, the compression processcan be an industry standard compression process such as, for example, agzip conversion technique.

At 150, the converted key value file undergoes an encryption process tocreate an encrypted key value file. In some embodiments, the encryptionprocess can be an industry standard encryption process such as, forexample, a hashing encryption process, a symmetric encryption process,an asymmetric encryption process, etc. For example, in some embodiments,the encryption process can be a data encryption standard (DES) process,an advanced encryption standard (AES) process, a proposed encryptionstandard, etc. It will be appreciated that in some embodiments, the keyvalue file can undergo the encryption process at 150 prior to undergoingthe conversion process at 145.

As an example, a text file of the English nursery rhyme “Humpty Dumpty”can be converted by a computer device using the data conversion method100 as follows.

In this example, a memory portion of the computer device includes a textreference library of common words and their respective key value. Aportion of the text reference library is shown in Table 1 below.

TABLE 1 File Segment Key Value “a” 1 “again” 20 “all” 12 “and” 6“couldn't” 112 “fall” 84 “great” 93 “had” 31 “horses” 105 “king's” 152“men” 48 “on” 18 “put” 59 “sat” 62 “the” 2 “together” 44 “wall” 87

In this example, the computer device converts the text file into a rawfile that includes only the text within the raw file (105), as shownbelow:

-   -   Humpty Dumpty sat on a wall. Humpty Dumpty had a great fall. All        the king's horses and all the kings men couldn't put Humpty        together again.

While not provided in this example, it will be appreciated to oneskilled in the art that in some embodiments the raw file can becompressed before proceeding further.

The computer device then partitions the text of the raw file byseparating out each word (110). Each word is then compared to the textreference library (115). For each match the corresponding key value isobtained (120). The computer device uses the key values to create a keyvalue file that is representative of the raw file, as shown below (125).

-   -   Humpty Dumpty 62 18 1 87. Humpty Dumpty 31 193 84. 12 152 105 6        12 2 152 48 112 59 Humpty 44 20.

When the computer device determines that the text reference library doesnot have a match for the terms “Humpty” and “Dumpty”, the computerdevice updates the reference library with these new terms and creates anew key value for these terms (13). A portion of the updated textreference library is shown in Table 2 below.

TABLE 2 File Segment Key Value “a” 1 “again” 20 “all” 12 “and” 6“couldn't” 112 “Dumpty” 876 “fall” 84 “great” 93 “had” 31 “horses” 105“Humpty” 877 “king's” 152 “men” 48 “on” 18 “put” 59 “sat” 62 “the” 2“together” 44 “wall” 87

The computer device uses the newly created key values to update the keyvalue file (125), as shown below.

-   -   877 876 62 18 1 87. 877 876 31 193 84. 12 2 152 105 6 12 2 152        48 112 59 877 44 20.

Once, the computer device determines that all of the raw file segmentsare replaced with a key value (135), the computer device can thencompress (145) and encrypt (150) the key value file.

It is appreciated that a file converted using the data conversion method100 can be decompressed by reversing the data conversion method 100described above. In particular, a computer device can first decrypt anddecompress the key value file. The computer device can then compare eachkey value of the key value file with a key value stored in a referencelibrary of a raw file segment database. The computer device can thencreate a raw file by replacing each of the key values with thecorresponding raw file segment. The computer device can then convert thegenerated raw file into a data file.

With further reference to FIG. 2, one example of a data conversionsystem 200 capable of implementing a data conversion method, such as thedata conversion method 100 shown in FIG. 1, is illustrated. The datasystem network 200 includes a plurality of client modules 205 connectedto a data conversion server 210 via a data network 215.

Each of the client modules 205 includes a backup portion 220 connectedto a local conversion portion 225 and a local existing file segmentdatabase 230 via a connection 235. The data conversion server 210includes a master conversion portion 240 connected to a master existingfile segment database 245 via a connection 250.

In some embodiments, the client modules 205 can be a single computerdevice. In these embodiments, the backup portion 220 and the localconversion portion 225 can be part of a processor (not shown) and thelocal existing file segment database 230 can be part of a memory (notshown). The connection 235 can be a wired or wireless connectionconnecting the backup portion 220, the local conversion portion 225 andthe local existing file segment database 230 to each other.

In other embodiments, the client modules 205 can be a distributednetwork of computer devices or a binary component. For example, in oneembodiment, the backup portion 220 and the local conversion portion 225can each be a server device with the local existing file segmentdatabase 230 stored in a local cache memory of the local conversionportion 225. The connection 235 can be wired network, a wirelessnetwork, or a combination thereof. When the connection 235 is a wirelessnetwork, the connection 235 can be a public network like the Internet orother wide area network (WAN), a local area network (LAN), a privatenetwork, or combinations thereof.

The data network 215 can be a wireless network, a wired network, or acombination thereof. When the data network 215 is a wireless network,the data network 215 can be a public network like the Internet or otherwide area network (WAN), a local area network (LAN), a private network,or combinations thereof.

In some embodiments, the data conversion server 210 can be a singleserver device. In these embodiments, the master conversion portion 240can be part of the processor of the data conversion server 210 and themaster existing file segment database 245 can be part of the memory ofthe data conversion server 210. The connection 250 can be a wired orwireless connection connecting a processor of the data conversion server210 to the memory storing the master existing file segment database 245.

In other embodiments, the data conversion server 210 can be adistributed network of server devices connected via a cloud-computingarchitecture. For example, in one embodiment, the master conversionportion 240 can be a single server device or a plurality of serverdevices connected via the connection 250. Also, the master existing filesegment database 245 can be a single server device or a plurality ofserver devices connected via the connection 250. The one or more serverdevices that form the master conversion portion 240 and the one or moreserver devices that form the master existing file segment database 245are also connected via the connection 250.

The connection 250 can be wired network, a wireless network, or acombination thereof. When the connection 250 is a wireless network, theconnection 250 can be a public network like the Internet or other widearea network (WAN), a local area network (LAN), a private network, orcombinations thereof.

In operation, the backup portion 220 is configured to convert a file tobe converted into a raw file and send the raw file to the localconversion portion 225.

The local conversion portion 225 is configured to partition the raw fileinto a plurality of raw file segments. The local conversion portion 225is also configured to work with the local existing file segment database230 to replace each of the raw file segments with a key value.

The local existing file segment database 230 is configured to storeexisting raw file segments and key values. Each of the key values isassociated with a particular raw file segment. Accordingly, the localconversion portion 225 can compare each raw file segment partitionedfrom the raw file with the plurality of existing raw file segmentsstored in the local existing file segment database 230. In someembodiments, the local existing file segment database 230 can beconfigured to only store existing raw file segments and associated keyvalues for existing raw file segments previously used by the particularlocal conversion portion 225 of the client module 205.

When the local conversion portion 225 finds an existing raw file segmentin the local existing file segment database 230 that matches a raw filesegment partitioned from the raw file, the local existing file segmentdatabase 230 can provide a key value associated with the existing rawfile segment to the local conversion portion 225. The local conversionportion 225 can then build a key value file by replacing the raw filesegments with key values from the local existing file segment database230. In some embodiments, the local conversion portion 225 can also beconfigured to compress and/or encrypt the generated key value file.

When the local conversion portion 225 does not find an existing raw filesegment in the local existing file segment database 230, the localconversion portion 225 can communicate a request with the dataconversion server 210 via the data network 215 for a key value.

The master conversion portion 240 is configured to work with the masterexisting file segment database 245 to determine a key value for a rawfile segment sent from the client modules 205.

The master existing file segment database 245 is configured to storeexisting raw file segments and associate key values previously used byeach of the client modules 205. The master conversion portion 240 cancompare the raw file segment sent from one of the client modules 205with the plurality of existing raw file segments stored in the masterexisting file segment database 245.

When the master conversion portion 240 finds an existing raw filesegment in the master existing file segment database 245 that matchesthe raw file segment sent from one of the client modules 205, the masterconversion portion 240 can send a key value associated with the existingraw file segment to the client module 205. The local existing filesegment database 230 can then store the raw file segment as an existingraw file segment and store the associated key value for future use bythe client module 205.

When the master conversion portion 240 does not find an existing rawfile segment in the master existing file segment database 245, themaster conversion portion 240 is configured to generate a new key valuefor the existing raw file segment and store the raw file segment as anexisting raw file segment in the master existing file segment database245 with the newly generated key value. The master conversion portion240 is also configured to send the newly generated key value to theclient module 205.

In some embodiments, the master conversion portion 240 can also beconfigured to receive a key value file from one of the client modules205, compress and/or encrypt the key value file, and send the compressedand/or encrypted key value file back to the client module 205.

A data file converted using the data conversion system 200 can be usedfor secure transmission of data from one location to another, securedata backup, and general data storage. In particular, as the converteddata file may have a significantly smaller size than the data file priorto conversion, the data conversion system 200 can increase a speed inwhich the content of the data file is transmitted from one location toanother. The receiving location can then decompress the converted datafile to obtain the content of the data file. Also, as the converted datafile created by the data conversion system 200 can have a significantlysmaller size than the data file prior to conversion, the data conversionsystem 200 can increase the amount of content provided in the data filesthat can be stored in a data storage or used as a data backup.

FIG. 3 is a schematic diagram of an exemplary architecture for acomputer device 500, such as the one or more computer devices used asthe client module 205 and the server module 210. The computer device 500and 520 any of the individual components thereof can be used for any ofthe operations described in accordance with any of thecomputer-implemented methods described herein.

The computer device 500 generally includes a processor 510, memory 520,a network input/output (I/O) 525, storage 530, and an interconnect 550.The computer device 500 can optionally include a user I/O 515, accordingto some embodiments. The computer device 500 can be in communicationwith one or more additional computer devices 500 through a network 540.

The computer device 500 is generally representative of hardware aspectsof a variety of user devices 501 and a server device 535. Theillustrated user devices 501 are exemplary and are not intended to belimiting. Examples of the user devices 501 include, but are not limitedto, a desktop computer 502, a cellular/mobile phone 503, a tablet device504, and a laptop computer 505. It is to be appreciated that the userdevices 501 can include other devices such as, but not limited to, apersonal digital assistant (PDA), a video game console, a television, orthe like. In some embodiments, the user devices 501 can alternatively bereferred to as client modules 501. In such embodiments, the clientmodules 501 can be in communication with the server device 535 throughthe network 540. One or more of the client modules 501 can be incommunication with another of the client modules 501 through the network540 in some embodiments.

The processor 510 can retrieve and execute programming instructionsstored in the memory 520 and/or the storage 530. The processor 510 canalso store and retrieve application data residing in the memory 520. Theinterconnect 550 is used to transmit programming instructions and/orapplication data between the processor 510, the user I/O 515, the memory520, the storage 530, and the network I/O 540. The interconnect 550 can,for example, be one or more busses or the like. The processor 510 can bea single processor, multiple processors, or a single processor havingmultiple processing cores. In some embodiments, the processor 510 can bea single-threaded processor. In some embodiments, the processor 510 canbe a multi-threaded processor.

The user I/O 315 can include a display 316 and/or an input 317,according to some embodiments. It is to be appreciated that the user I/O315 can be one or more devices connected in communication with thecomputer device 500 that are physically separate from the computerdevice 500. For example, the display 516 and input 517 for the desktopcomputer 502 can be connected in communication but be physicallyseparate from the computer device 500. In some embodiments, the display316 and input 517 can be physically included with the computer device500 for the desktop computer 502. In some embodiments, the user I/O 515can physically be part of the user device 501. For example, thecellular/mobile phone 503, the tablet device 504, and the laptop 505include the display 516 and input 517 that are part of the computerdevice 500. The server device 535 generally may not include the user I/O515. In some embodiments, the server device 535 can be connected to thedisplay 516 and input 517.

The display 516 can include any of a variety of display devices suitablefor displaying information to the user. Examples of devices suitable forthe display 516 include, but are not limited to, a cathode ray tube(CRT) monitor, a liquid crystal display (LCD) monitor, a light emittingdiode (LED) monitor, or the like.

The input 517 can include any of a variety of input devices or meanssuitable for receiving an input from the user. Examples of devicessuitable for the input 517 include, but are not limited to, a keyboard,a mouse, a trackball, a button, a voice command, a proximity sensor, anocular sensing device for determining an input based on eye movements(e.g., scrolling based on an eye movement), or the like. It is to beappreciated that combinations of the foregoing inputs 517 can beincluded for the user devices 501. In some embodiments the input 517 canbe integrated with the display 516 such that both input and output areperformed by the display 516.

The memory 520 is generally included to be representative of a randomaccess memory such as, but not limited to, Static Random Access Memory(SRAM), Dynamic Random Access Memory (DRAM), or Flash. In someembodiments, the memory 520 can be a volatile memory. In someembodiments, the memory 520 can be a non-volatile memory. In someembodiments, at least a portion of the memory can be virtual memory.

The storage 530 is generally included to be representative of anon-volatile memory such as, but not limited to, a hard disk drive, asolid state device, removable memory cards, optical storage, flashmemory devices, network attached storage (NAS), or connections tostorage area network (SAN) devices, or other similar devices that maystore non-volatile data. In some embodiments, the storage 530 is acomputer readable medium. In some embodiments, the storage 530 caninclude storage that is external to the computer device 500, such as ina cloud.

The network I/O 525 is configured to transmit data via a network 540.The network 540 may alternatively be referred to as the communicationsnetwork 540. Examples of the network 540 include, but are not limitedto, a local area network (LAN), a wide area network (WAN), the Internet,or the like. In some embodiments, the network I/O 525 can transmit datavia the network 540 through a wireless connection using WiFi, Bluetooth,or other similar wireless communication protocols. In some embodiments,the computer device 500 can transmit data via the network 540 through acellular, 3G, 4G, or other wireless protocol. In some embodiments, thenetwork I/O 525 can transmit data via a wire line, an optical fibercable, or the like. It is to be appreciated that the network I/O 525 cancommunicate through the network 540 through suitable combinations of thepreceding wired and wireless communication methods.

The server device 535 is generally representative of a computer device500 that can, for example, respond to requests received via the network540 to provide, for example, data for rendering a website on the userdevices 501. The server device 535 can be representative of a dataserver, an application server, an Internet server, or the like.

Aspects described herein can be embodied as a system, method, orcomputer readable medium. In some embodiments, the aspects described canbe implemented in hardware, software (including firmware or the like),or combinations thereof. Some aspects can be implemented in a computerreadable medium, including computer readable instructions for executionby a processor. Any combination of one or more computer readablemedium(s) can be used.

The computer readable medium can include a computer readable signalmedium and/or a computer readable storage medium. A computer readablestorage medium can include any tangible medium capable of storing acomputer program for use by a programmable processor to performfunctions described herein by operating on input data and generating anoutput. A computer program is a set of instructions that can be used,directly or indirectly, in a computer system to perform a certainfunction or determine a certain result. Examples of computer readablestorage media include, but are not limited to, a floppy disk; a harddisk; a random access memory (RLA); a read-only memory (ROM); asemiconductor memory device such as, but not limited to, an erasableprogrammable read-only memory (EPROM), an electrically erasableprogrammable read-only memory (EEPROM), Flash memory, or the like; aportable compact disk read-only memory (CD-ROM); an optical storagedevice; a magnetic storage device other similar device; or suitablecombinations of the foregoing. A computer readable signal medium caninclude a propagated data signal having computer readable instructions.Examples of propagated signals include, but are not limited to, anoptical propagated signal, an electro-magnetic propagated signal, or thelike. A computer readable signal medium can include any computerreadable medium that is not a computer readable storage medium that canpropagate a computer program for use by a programmable processor toperform functions described herein by operating on input data andgenerating an output.

Some embodiments can be provided to an end-user through acloud-computing infrastructure. Cloud computing generally includes theprovision of scalable computing resources as a service over a network(e.g., the Internet or the like).

Although a number of methods and systems are described herein, it iscontemplated that a single system or method can include more than one ofthe above discussed subject matter. Accordingly, multiple of the abovesystems and methods can be used together in a single system or method.

The examples disclosed in this application are to be considered in allrespects as illustrative and not limitative. The scope of the inventionis indicated by the appended claims rather than by the foregoingdescription; and all changes which come within the meaning and range ofequivalency of the claims are intended to be embraced therein.

The invention claimed is:
 1. A data conversion system for converting adata file, comprising a client module that includes: a backup portionoperated by a first processor and configured to convert data stored inthe data file into raw data, the raw file composed of raw data that is alower level of data than data stored in the data file, a conversionportion operated by a second processor and connected to the backupportion, the conversion portion configured to partition the raw fileinto a plurality of raw file segments, and an existing raw file segmentlibrary portion that is part of a memory and configured to store one ormore existing raw file segments and one or more key values, each of theone or more key values associated with one of the one or more existingraw file segments, wherein the conversion portion is also configured toassign a key value to each of the plurality of raw file segments and tocreate a key value file with the assigned key values, wherein theconversion portion is configured to, for each of the plurality of rawfile segments, compare the raw file segment to one or more existing rawfile segments stored in the existing file segment library portion,wherein when the raw file segment does not match any of the one or moreexisting raw file segments, the existing raw file segment libraryportion is configured to store the raw file segment, and the conversionportion is configured to create and store a key value associated withthe raw file segment into the existing raw file segment library portion,and wherein a size of each of the plurality of key values is less thanor equal to a size of the raw file segment associated with theparticular key value.
 2. The data conversion system of claim 1, whereinthe conversion portion is configured to encrypt the key value file. 3.The data conversion system of claim 1, wherein the conversion portion isconfigured to compress the key value file.
 4. The data conversion systemof claim 1, wherein the conversion portion is configured to change a keyvalue associated with an existing raw file segment based on a frequencyof the existing raw file segment matching one of the plurality of rawfile segments.
 5. The data conversion system of claim 4, wherein achanged key value changed based on the frequency of the existing rawfile segment matching one of the plurality of raw file segments has asmaller size than a previous key value associated with the existing rawfile segment.
 6. The data conversion system of claim 1, wherein the rawfile composed of the raw data is in a cross global format.
 7. The dataconversion system of claim 6, wherein the cross global format is abinary code format.
 8. The data conversion system of claim 1, whereinthe raw file composed of the raw data is in an American Standard Codefor Information Interchange (ASCII) data format.
 9. The data conversionsystem of claim 1, wherein the raw file is a binary code file and theraw data is binary code data.
 10. The data conversion system of claim 9,wherein the conversion portion is configured to partition the binarycode file into a plurality of binary strings.
 11. The data conversionsystem of claim 1, wherein the conversion portion is configured topartition the raw file into the plurality of raw file segments based ona variable size delimiter in which one or more of the plurality of rawfile segments is segmented at a gap or space in the raw file.
 12. Thedata conversion system of claim 1, wherein the conversion portion isconfigured to partition the raw file into the plurality of raw filesegments based on a fixed size delimiter in which one or more of theplurality of raw file segments is segmented to have a fixed memory size.13. The data conversion system of claim 1, wherein the conversionportion is configured to partition the raw file into the plurality ofraw file segments based on a variable size delimiter in which one ormore of the plurality of raw file segments is segmented at a gap orspace in the raw file and on a fixed size delimiter in which the one ormore of the plurality of raw file segments is segmented to have a fixedmemory size when a gap or space is not present within a portion of theraw file extending along the fixed memory size.
 14. The data conversionsystem of claim 1, wherein the existing raw file segment library portionincludes a plurality of reference libraries, wherein each of thereference libraries is provided to store one or more of the existing rawfile segments of a particular file type.
 15. The data conversion systemof claim 14, wherein the existing raw file segment library portionincludes at least one of a text file reference library, a video filereference library, and an application file reference library.
 16. Thedata conversion system of claim 1, wherein the key value is ahexadecimal value.
 17. The data conversion system of claim 1, whereinthe key value is an ASCII value.
 18. The data conversion system of claim1, wherein the conversion portion is configured to create the key valuefile after assigning a particular key value of the plurality of keyvalues to each of the plurality of raw file segments.
 19. The dataconversion system of claim 1, wherein the conversion portion isconfigured to create and update the key value file while assigning aparticular key value of the plurality of key values to each of theplurality of raw file segments.
 20. The data conversion system of claim1, wherein the first processor and the second processor are the sameprocessor.